fix: string values starting with \n exported as invalid YAML literal block#128
Merged
xiwenc merged 1 commit intomxlint:mainfrom Apr 29, 2026
Merged
Conversation
Member
|
thanks Furkan! This does indeed solve your specific case. Will accept it for now. Will look into this in more detail to have a more structural solution that works in "all" cases. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
String fields whose value starts with a newline (e.g. expression values) were exported with a |4 literal block indicator, producing invalid YAML that caused the linter to crash with Error parsing YAML file.
Root cause: after indent-stripping, the leading \n was still present, triggering the multiline code path even when the actual content is a single line. The fix trims leading newlines before the multiline check so these values are exported as plain scalars.